LISP stretched subnet mode for data center migrations

ABSTRACT

The present disclosure describes methods and systems for enabling a migration of network elements from a first location to a second location remote from the first location without changing the Internet Protocol (IP) addresses, subnet mask, and/or default gateway of the network elements. The first location has a first Locator/Identifier Separation Protocol (LISP) router configured on a stick and the second location having a second LISP router configured on a stick. Both the first LISP router and the second LISP router are on the same subnet. Effectively, LISP provides a Layer 3 extension stretching a subnet across the first location and the second location (Stretched Subnet Mode (SSM)). By implementing LISP routers in this manner, system engineers can migrate network elements easily between two locations.

CROSS-REFERENCE TO RELATED APPLICATION

This Application is a continuation (and claims the benefit of priorityunder 35 U.S.C. §120) of U.S. application Ser. No. 14/220,922 (InventorsSantiago Vazquez Freitas, et al.), filed Mar. 20, 2014 and entitled“LISP STRETCHED SUBNET MODE FOR DATA CENTER MIGRATIONS”. The disclosureof the prior application is considered part of the disclosure of thisapplication and is incorporated in its entirety by reference.

TECHNICAL FIELD

This disclosure relates in general to the field of communications and,more particularly, to using Locator/Identifier Separation Protocol(LISP) in stretched subnet mode for data center migrations.

BACKGROUND

A common requirement during data center (DC) migrations is the abilityto move the servers (physical or virtual) between DCs while keepingtheir IP address. Changing the servers' IP addresses, subnet and defaultgateway configurations is cumbersome and costly so most application andserver teams would prefer to avoid it.

BRIEF DESCRIPTION OF THE DRAWINGS

To provide a more complete understanding of the present disclosure andfeatures and advantages thereof, reference is made to the followingdescription, taken in conjunction with the accompanying figures, whereinlike reference numerals represent like parts, in which:

FIG. 1A is a simplified block diagram illustrating a migration of anetwork element, where when the network element moves from location 1 tolocation 2, its IP address changes because its IP address represents itsidentity and location;

FIG. 1B is a simplified block diagram illustrating a migration of anetwork element, where when the network element moves from location 1 tolocation 2 its IP address configuration (its identity) doesn't change,only its location changes, according to some embodiments of thedisclosure;

FIG. 2 is a simplified flow diagram illustrating methods for enabling amigration of network elements from a first location to a second locationwithout changing the IP addresses of the network elements, according tosome embodiments of the disclosure;

FIG. 3 is a simplified diagram showing an exemplary system having LISProuters for enabling migration of servers from an original data centerto a target data center, according to some embodiments of thedisclosure;

FIG. 4 is a simplified diagram showing a data path between a server thathas not been moved yet but is on the subnet where mobility is needed anda network element on the wide area network, according to someembodiments of the disclosure;

FIG. 5 is a simplified diagram showing detection of a server on thesubnet where mobility is needed; according to some embodiments of thedisclosure;

FIG. 6 is a simplified diagram showing updating of a mapping databaseand its cache(s) for at least two LISP routers after a server ismigrated to the target data center;

FIG. 7 is a simplified diagram showing the LISP Router responding toaddress resolution protocol request for the migrated server in order toroute traffic targeted to the migrated server via the LISP router at theoriginal data center, according to some embodiments of the disclosure;

FIG. 8 is a simplified diagram showing a LISP tunnel for transportingLISP-encapsulated packets between a LISP router at the original datacenter and a LISP router at the target data center in order to routetraffic from a network element on the wide area network to the migratedserver, according to some embodiments of the disclosure;

FIG. 9 is a simplified diagram showing a LISP tunnel for transportingLISP-encapsulated packets between a LISP router at the original datacenter and a LISP router at the target data center in order to routeintra-subnet traffic from a network element on the subnet at theoriginal data center to the migrated server, according to someembodiments of the disclosure;

FIG. 10 is a simplified diagram showing a LISP router at the originaldata center for providing return traffic to a stateful device at theoriginal data center, according to some embodiments of the disclosure;

FIGS. 11A-B illustrates possible deployment models of LISP routers;

FIG. 11C illustrates a deployment model corresponding to using LISP toenable migration of network elements without having to change the IPaddresses of the network element, according to some embodiments of thedisclosure; and

FIG. 12 shows an exemplary system diagram of an illustrative LISProuter, according to some embodiments of the disclosure.

DETAILED DESCRIPTION OF EXAMPLE EMBODIMENTS Overview

A method for enabling a migration of network elements from a firstlocation to a second location remote from the first location withoutchanging the Internet Protocol (IP) addresses, subnet mask, and/ordefault gateway of the network elements is disclosed. The first locationhas a first Locator/Identifier Separation Protocol (LISP) routerconfigured on a stick and the second location has a second LISP routerconfigured on a stick. Both the first LISP router and the second LISProuter are on the same subnet. The first LISP router detects a firstnetwork element having a first Internet Protocol (IP) address at thefirst location prior to the migration. The first LISP router receives,via a mapping database (from second LISP router at the second location)after the migration, an entry mapping the first IP address to the IPaddress of the second LISP router. The first LISP router updates a cacheof the mapping database of the first LISP router to configure the firstLISP router to route traffic targeted to the first network elementthrough the first LISP router.

In some embodiments, the first LISP router transmits, to a first switchat the first location to which the first LISP is connected on a stick,an address resolution protocol message to inform the first switch toroute the traffic targeted to the first network element via the firstLISP router.

In some embodiments, the first LISP router acting as a proxy transmits,to the second LISP router, the traffic targeted to the first networkelement over a LISP tunnel established between the first LISP router andthe second LISP router.

In some embodiments, the first LISP router encapsulating the traffictargeted to the first network element as LISP-encapsulated packets priorto transmitting the traffic over the LISP tunnel.

In some embodiments, the first LISP router removes virtual local areanetwork information associated with the first location from the traffictargeted to the first network element prior to transmitting the trafficover the LISP tunnel.

In some embodiments, the first LISP router receives, from the secondLISP router, return traffic from the first network element at the secondlocation and transmits the return traffic from the first network elementon an internal interface to provide the return traffic to a statefuldevice at the first location.

Another method for enabling a migration of network elements from a firstlocation to a second location remote from the first location withoutchanging the Internet Protocol (IP) addresses, subnet mask, and/ordefault gateway of the network elements is disclosed. The first locationhas a first Locator/Identifier Separation Protocol (LISP) routerconfigured on a stick and the second location has a second LISP routerconfigured on a stick. Both the first LISP router and the second LISProuter are on the same subnet. The second LISP router detects a firstnetwork element having a first IP address at the second location,wherein the first network element was connected to the subnet at thefirst location prior to the migration using the same first IP address.The second LISP router updates a mapping database to include an entrymapping the first IP address to the IP address of the second LISProuter. The second LISP router transmits, via the mapping database tothe first LISP router, the entry to update a cache of the mappingdatabase at the first LISP router to configure the first LISP router toroute, to the second LISP router, traffic targeted to the first networkelement through the first LISP router.

In some embodiments, the second LISP router receives, from the firstLISP router acting as a proxy via a LISP tunnel established between thefirst LISP router and the second LISP router, the traffic targeted tothe first network element.

In some embodiments, the traffic targeted to the first network elementoriginates from a second network element connected to a wide areanetwork.

In some embodiments, the traffic targeted to the first network elementoriginates from a third network element connected to the same ordifferent subnet at the first location.

In some embodiments, the second LISP router is configured with the sameIP address as a default gateway address used by the first networkelement prior to the migration.

A first Locator/Identifier Separation Protocol (LISP) router forenabling a migration of network elements from a first location to asecond location remote from the first location without changing theInternet Protocol (IP) addresses of the network elements is disclosed.The first LISP router is connected to a first switch on a stick at thefirst location. The first LISP router includes: at least one memoryelement; at least one processor coupled to the at least one memoryelement. The first LISP router further includes a LISP routing modulethat when executed by the at least one processor is configured to:detect, at the first LISP router, a first network element having a firstInternet Protocol (IP) address at the first location prior to themigration; receive, from a second LISP router at the second locationafter the migration via a mapping database, an entry mapping the firstIP address to the IP address of the second LISP router, wherein thesecond LISP router is configured on a stick to a second switch at thesecond location and both the first LISP router and the second LISProuter on the same subnet; and update a cache of a mapping database atthe first LISP router to configure the first LISP router to route, tothe second LISP router, traffic targeted to the first network elementthrough the first LISP router.

In some embodiments, prior to the migration, the first LISP routerconnected to a first switch on a stick is not in a data path between thefirst network element and a second network element on the wide areanetwork or between the first network element and a third network elementlocated in the first location.

In some embodiments, the first LISP router is configured as a LISP proxyingress and egress tunnel router to transmit the traffic targeted to thefirst network element via a LISP tunnel established between the firstLISP router and the second LISP router.

A second Locator/Identifier Separation Protocol (LISP) router forenabling a migration of network elements from a first location to asecond location remote from the first location without changing theInternet Protocol (IP) addresses of the network elements is disclosed.The second LISP router is connected to a second switch on a stick at thesecond location. The second LISP router includes: at least one memoryelement; at least one processor coupled to the at least one memoryelement. The second LISP router further includes a LISP routing modulethat when executed by the at least one processor is configured to:detect, at the second LISP router, a first network element having afirst IP address at the second location, wherein the first networkelement was connected to a subnet at the first location prior to themigration using the same first IP address; update a mapping database toinclude an entry mapping the first IP address to the IP address of thesecond LISP router; and transmit to the first LISP router via themapping database, the entry to update a cache of the mapping database atthe first LISP router to configure the first LISP router to route, tothe second LISP router, traffic targeted to the first network elementthrough the first LISP router, wherein the first LISP router isconfigured on a stick to a first switch at the first location and boththe first LISP router and the second LISP router on the same subnet.

In some embodiments, the second LISP router is configured as an LISPingress and egress tunnel router with a mapping server and a mappingresolver implemented thereon to maintain the mapping database andtransmit updates to a cache of the mapping database at the first LISProuter.

A system for enabling a migration of network elements from a firstlocation to a second location remote from the first location withoutchanging the Internet Protocol (IP) addresses of the network elements isdisclosed. The system includes a first LISP router configured on a stickto a first switch at the first location; a second LISP router configuredon a stick to a second switch at the second location, wherein both thefirst LISP router and the second LISP router on the same subnet; and ahorizontal LISP tunnel between the first LISP router and the second LISProuter providing a Layer 3 extension stretching a subnet across thefirst location and the second location. The second LISP router isconfigured to, via a mapping database, update a cache of the mappingdatabase at the first LISP router to configure the first LISP router toroute, via the first LISP router over the horizontal LISP tunnel,traffic targeted to a first network element migrated from the firstlocation to the second location.

In some embodiments, the cache of the mapping database at the first LISProuter and a cache of the mapping database of the second LISP routereach comprises an entry mapping a first IP address of the first networkelement to the IP address of the second LISP router, wherein the firstnetwork element was connected to a subnet at the first location prior tothe migration using the same first IP address.

A computer-readable non-transitory medium comprising one or moreinstructions, for enabling a migration of network elements from a firstlocation to a second location remote from the first location withoutchanging the Internet Protocol (IP) addresses, subnet mask, and defaultgateway of the network elements is disclosed. The first location has afirst Locator/Identifier Separation Protocol (LISP) router configured ona stick and the second location has a second LISP router configured on astick. Both the first LISP router and the second LISP router are on thesame subnet. When the instructions are executed on a processor, theinstructions configure the processor to perform one or more operationscomprising: detecting, by the first LISP router, a first network elementhaving a first Internet Protocol (IP) address at the first locationprior to the migration; receiving, at the first LISP router via amapping database from a second LISP router at the second location afterthe migration, an entry mapping the first IP address to the IP addressof the second LISP router; and updating, by the first LISP router, acache of the mapping database at the first LISP router to configure thefirst LISP router to route, to the second LISP router, traffic targetedto the first network element through the first LISP router.

A computer-readable non-transitory medium comprising one or moreinstructions, for enabling a migration of network elements from a firstlocation to a second location remote from the first location withoutchanging the Internet Protocol (IP) addresses, subnet mask, and defaultgateway of the network elements is disclosed. The first location has afirst Locator/Identifier Separation Protocol (LISP) router configured ona stick and the second location has a second LISP router configured on astick. Both the first LISP router and the second LISP router are on thesame subnet. When the instructions are executed on a processor, theinstructions configure the processor to perform one or more operationscomprising: detecting, at the second LISP router, a first IP address ofa first network element located at the second location, wherein thefirst network element was connected to a subnet at the first locationprior to the migration using the same first IP address; updating, at thesecond LISP router, a the mapping database to include an entry mappingthe first IP address to the IP address of the second LISP router; andtransmitting, from the second LISP router via the mapping database tothe first LISP router, the entry to update a cache of the mappingdatabase at the first LISP to configure the first LISP router to route,to the second LISP router, traffic targeted to the first network elementthrough the first LISP router.

Example Embodiments Understanding Challenges in Migration

Migration of servers from a first location (e.g., an original datacenter) to a second location remote from the first location (e.g., atarget data center) is a task, which many server engineers face. Thesemigrations are often necessary to improve the performance of the serversby upgrading to a better data center, or to meet other requirements,which prompted servers to be moved from a first location to anotherlocation. However, these migrations between customer data centers (DCs)or from a legacy to a new environment within DCs. often take too long toperform. Usually, many services and network components depend on theInternet Protocol (IP) addresses of servers for correctly identifyingthe servers on the network. Thus, when servers migrate from a firstlocation to a second location, it is generally preferred that IPaddresses, subnet masks, and default gateway IP address do not changeduring or after migration. However, migration network solutions thatprovide IP retention can be unreliable, complex, and expensive. Forinstance, extending a Layer 2 domain between DCs to solve this problemis not always perceived as optimal in term of resiliency, due tobroadcast domain interconnection that could cause a failure in theoriginal DC to impact the target DC.

In many application deployments, each server has multiple NetworkInterface Cards and/or IP addresses belonging to multiple subnets. Whentrying to migrate such servers, this creates a high level of dependencybecause all the servers that exist on the same subnets as the server tobe migrated, also needs to be migrated at the same time, leading to a“Big Bang” migration where every server must be moved at the same time.The “Big Bang” approach impacts heavily the time and complexity of DCmigrations, and also requires that all the data (storage) for all theservers to be copied at once to the new DC. This is an extremelyunpractical approach, and thus is seldom performed.

Fundamentals of Locator/Identifier Separation Protocol (LISP)

FIG. 1A is a simplified block diagram illustrating a migration of anetwork element, where when the network element moves from location 1 tolocation 2, its IP address changes because its IP address represents itsidentity and location. The Internet architecture combines two functions,routing locators (where a client is attached to the network) andidentifiers (who the client is) in one number space: the IP address.Thus, when a network element migrates, the IP address necessarilychanges. In this illustration, a network element (shown as device 102 inthe FIGURE) has an Internet Protocol version 4 (IPv4) or InternetProtocol version 6 (IPv6) address, and such address (e.g., X.Y.Z.1)represents the network element's identity and its location. When thenetwork element moves from Location 1 to Location 2, the same networkelement (shown as device 104 in the FIGURE) gets a new IPv4 or IPv6address for its new identity and location.

Using a single address field for both identifying a device and fordetermining where it is topologically located in the network requiresoptimization along two conflicting axes: for routing to be efficient,the address must be assigned topologically; for collections of devicesto be easily and effectively managed, without the need for renumberingin response to topological change (such as that caused by adding orremoving attachment points to the network or by mobility events), theaddress must explicitly not be tied to the topology. Such a routing andaddressing system, which uses an IP address to represent both identityand location, is not scalable or flexible.

To address this routing and addressing issue, the Locator/IdentifierSeparation Protocol (LISP) (outlined in Internet Engineering Task Force(IETF) RFC 6830) was proposed. LISP is a “map-and-encapsulate” protocol,which aims to separate identity and location. The approach that LISPtakes to solving the routing scalability problem is to replace IPaddresses with two new types of numbers: Routing Locators (RLOCs), whichare topologically assigned to network attachment points (and aretherefore amenable to aggregation) and used for routing and forwardingof packets through the network; and Endpoint Identifiers (EIDs), whichare assigned independently from the network topology, are used fornumbering devices, and are aggregated along administrative boundaries.LISP then defines functions for mapping between the two numbering spacesand for encapsulating traffic originated by devices using non-routableEIDs for transport across a network infrastructure that routes andforwards using RLOCs. Both RLOCs and EIDs are syntactically identical toIP addresses; it is the semantics of how they are used that differs.

Broadly speaking, LISP provides a network-layer-based protocol thatenables separation of IP addresses into two new numbering spaces: EIDsand RLOCs. No changes are required to either host protocol stacks or tothe “core” of the Internet infrastructure. Locator/Identifier SeparationProtocol (LISP) provides a set of functions for routers to exchangeinformation used to map from EIDs that are not globally routable toroutable RLOCs. A mapping database and caches of said mapping databaseis provided to LISP routers which maps EIDs to RLOCs, and a LISP routingmodule is provided to equipment such as routers to perform routing basedon the mapping database or a cache thereof. LISP also defines amechanism for these LISP routers to encapsulate IP packets addressedwith EIDs for transmission across a network infrastructure that usesRLOCs for routing and forwarding.

FIG. 1B is a simplified block diagram illustrating a migration of anetwork element, where when the network element moves from location 1 tolocation 2 its IP address configuration (its identity) does not change,only its location changes, according to some embodiments of thedisclosure. By applying LISP protocol, a network element (shown asdevice 106 in the FIGURE) has an Internet Protocol version 4 (IPv4) orInternet Protocol version 6 (IPv6) address, and such address (e.g.,X.Y.Z.1) represents the network element's identity only. When thenetwork element moves from Location 1 to Location 2, the same networkelement (shown as device 108 in the FIGURE) keeps the same IP address(i.e., its identity), and only the location changes.

Adapting LISP for Improving Migrations: Stretched Subnet Mode

LISP was not originally really designed for DC migrations. Inparticular, LISP's intended use cases included Efficient Multi-HomingSupport, IPv6 Transition, Virtualization/Multi-Tenancy Support and, DCVM-Mobility Support and LISP Mobile-Node Support. Even though LISP isnot intended for migration of network elements, the technical andarchitectural features of LISP can be adapted and leveraged to meet therequirements of users who want to perform server migration withoutextending Layer 2 between locations. Specifically, LISP can be adaptedin such a way that is analogous to a Layer 3 extension.

The present disclosure describes how migration can be achieved withoutLayer 2 extension by diverting LISP IP mobility to enable a migration ofnetwork elements from a first location (e.g., an original data center)without changing their IP addresses, subnet mask, and default gatewayand landing the network elements on at a second location remote from thefirst location (e.g., a target data center) on the same subnet that thenetwork elements were using at the first location. Effectively, LISPprovides a Layer 3 extension stretching a subnet across the firstlocation and the second location (referred herein as Stretched SubnetMode (SSM)). Note that Stretched Subnet Mode (SSM) is not LISP ExtendedSubnet Mode (ESM) because there is no Layer 2 extension between the twolocations, and it is also not Across Subnet Mode (ASM) because thesubnet on the second location is the same as the one at the firstlocation, not a new (foreign) one.

Through Stretched Subnet Mode (SSM), network elements such as physicalor virtual servers can be migrated from one location to another withoutchanging their IP address, subnet mask, default gateway, firewall rules,and/or load balancer statements. SSM effectively lets users to performmigrations in very small batches or waves (i.e., small group of servers)which enables them to start the migration sooner and finish it quicker.Also, with small migration waves, only the data (storage) associatedwith the servers being migrated need to be copied to the new site,hugely minimizing the amount of data that has to be copied between thesites before a server migration can start.

Besides allowing migration to be performed in small waves, LISP SSM hasanother advantage—LISP routers applying SSM can be deployednon-disruptively into an existing/production environment. Deployment caninclude two LISP nodes (a first LISP router at the first location and asecond LISP router at the second location). For instance, a first LISProuter is connected to a switch at the first location on a stick, and asecond LISP router is connected to a switch at the second location on astick. The “router on a stick” configuration allows these LISP routersto be deployed without any major changes to the Wide Area Network or thefirst location (e.g., the existing data center, in some cases havinglegacy network equipment). The only effect SSM has at the first locationis on the switch at the first location, where a port configured as trunk(IEEE 802.1Q) allowing the VLANs for the subnets to be migrated isconnected to the LISP router that also has its interface configured asIEEE 802.1Q trunk—this is an example configuration on the switch toconfigure the first LISP router on a stick. Furthermore, at the end ofthe migration the two LISP routers can be smoothly removed from thenetwork without disrupting the second location. More LISP routers can bedeployed at the first location and/or the second location forredundancy.

A LISP router a stick means that the LISP router is not on the data pathuntil it is required to be. The LISP router on a stick can deployednon-intrusively as the LISP router on a stick is not the default gatewayfor network elements at original DC and is not on the data path until itis required to be because of a migration of a network element fromlocation 1 to location 2. In summary the LISP router on a stick is noton the data path nor is the LISP router the default gateway for networkelements at the original DC prior to migration.

FIG. 2 is a simplified flow diagram illustrating methods for enabling amigration of network elements from a first location to a second locationwithout changing the IP addresses of the network elements, according tosome embodiments of the disclosure. Specifically, the illustrated methodcomprises parts of the method performed by LISP routers for enabling amigration of network elements from a first location to a second locationremote from the first location without changing the Internet Protocol(IP) addresses of the network elements. The first location has a firstLocator/Identifier Separation Protocol (LISP) router configured on astick, and the second location has a second LISP router configured on astick.

For this method, a mapping database (system) is provided, which can bewith either the first LISP router or the second LISP router, to maintainentries mapping identities of network elements to the locations of theLISP routers via which the network elements are reachable. The mappingdatabase can also be provided on a separate LISP-enabled entity/systemapart from the first LISP router. The first LISP router and/or thesecond LISP router has a cache, which is a copy (requested on demand) ofat least a part of the mapping database to facilitate routing of LISPencapsulated packets. A LISP router detecting a new network element atthe location in which the LISP router is deployed can update the mappingdatabase with entry associating the identity of the network element withthe location of the LISP router. The LISP router can also update its owncache (if there is one at the LISP router) as well. By updating themapping database, the LISP router can transmit via the mapping database(system) the new entry to other LISP routers. In a way, the LISP routercauses other cache(s) of the mapping database to be updated with the newentry. This mechanism of the mapping database (system) and cache(s)allows routing to occur properly after the migration.

Prior to the migration, the first LISP router detects a first networkelement having a first Internet Protocol (IP) address at the firstlocation (box 202). At this point, the first LISP router can update themapping database (and a cache of the mapping database at the first LISProuter, if applicable) associating the location of the first LISP routerwith the first network element. The first network element is migratedfrom the first location to the second location (box 204). The secondLISP router detects the first network element having the first IPaddress at the second location (box 206) after the first network elementhas moved to the second location. The first network element wasconnected to a subnet at the first location prior to the migration usingthe same first IP address. SSM allows that original subnet to bestretched to the second location. This means that both the first LISProuter and the second LISP router are provided on the same/originalsubnet.

Upon detecting the first network element at the second location, thesecond LISP router updates a mapping database (and a cache of themapping database, if applicable) to include an entry mapping the firstIP address to the IP address of the second LISP router (box 208).Furthermore, the second LISP router transmits, e.g., via the mappingdatabase (system), to the first LISP router, the entry to update a cacheof the mapping database at the first LISP router to configure the firstLISP router to route, to the second LISP router, traffic targeted to thefirst network element through the first LISP router (box 210). The firstLISP router receives, via the mapping database (system) from a secondLISP router at the second location after the migration, an entry mappingthe first IP address to the IP address of the second LISP router andupdates the cache of the first LISP router to configure the first LISProuter to route, to the second LISP router, traffic targeted to thefirst network element through the first LISP router (box 212).

The result of updating the mapping database and the cache of the mappingdatabase at the first LISP router allows the first LISP router toattract traffic to the first network element and proxy that trafficthrough the first LISP router. Specifically, the first LISP routertransmits an Gratuitous Address Resolution Protocol (ARP) message andimplements proxy ARP (box 214) to employ a technique by which a firstLISP router answers the ARP queries for the first IP address (i.e.,corresponding to the first network element no longer at the firstlocation). The first LISP router as a proxy is aware of the location ofthe traffic's destination, and offers its own MAC address in reply,effectively saying, “send it to me, and I'll get it to where it needs togo.” Serving as a proxy for the first network element (and any othernetwork element migrated over to the second location) effectivelydirects traffic targeted to the network element to the first LISProuter. The “captured” traffic is then routed by the proxy to the firstnetwork element (or the suitable intended destination) via a LISP tunnelbetween the first LISP router and the second LISP router (box 216).

Implementing the mechanisms outlined in FIG. 2, traffic targeted to thefirst network element is able to travel from a second network element onthe wide area network or from a third network element at the firstlocation (e.g., connected to the subnet at the first location) via thefirst LISP router and over the LISP tunnel between the first LISP routerand the second LISP router. By providing this method, the first LISProuter and the second LISP router facilitates migration of networkelements without having to change the IP addresses of those networkelements, and allows migration to occur in small waves. The networkelements remains in the same subnet, even though the location of thenetwork elements have changed after the migration. The followingpassages explains each of these mechanisms in further detail.

LISP Router on a Stick

FIG. 3 is a simplified diagram showing an exemplary system having LISProuters for enabling migration of servers from an original data center(“original DC”) to a target data center (“target DC”), according to someembodiments of the disclosure. The original DC is considered as the“first location”, and the target DC is considered as the “secondlocation”. As shown, the first LISP router 302 a and another LISP router302 b are each configured on a stick for redundancy at the firstlocation. Even though redundant LISP routers are shown, it is notnecessary to provide redundant LISP routers. Accordingly, only one LISProuter can be deployed at each of the locations (and redundant routersas shown are omitted). It is envisioned that more or less (e.g., justone) LISP routers can be deployed at the first location. Also, thesecond LISP router 304 a and another LISP router 304 b are eachconfigured on a stick for redundancy at the second location. It isenvisioned that more or less (e.g., just one) LISP routers can bedeployed at the second location. For brevity, the present disclosurewill focus on an embodiment illustrating a system where a first LISProuter 302 a is provided on a stick to a switch at the first location,and a second LISP router 304 a is provided on a stick to a switch at thesecond location (without necessarily referring to the redundant routersshown on the FIGURES).

At the original data center, network elements (e.g., server 306 andserver 308) are connected to a subnet at the original data center. AnyVirtual Local Area Networks may exist and Spanning Tree Protocols may beused in the subnet at the original data center. The present disclosuredescribes an improved system and method for migrating these networkelements.

A second LISP router (e.g., LISP router 304 a) is also configured on astick to a switch at the second location. Prior to the migration, thesecond LISP router may not receive any traffic at all. Optionally, thesecond LISP router can be configured with the same IP address as adefault gateway address used by the first network element prior to themigration. Advantageously, the first network element does not have toupdate its default gateway address after the first network element movesto the second location. Network at the second location can have anyVirtual Local Area Networks, and implement practically any type of Layer2 technologies (spanning tree protocol, virtual port channels,multichassis EtherChannel, Transparent Interconnection of Lots of Links,etc.). It is noted, in particular, that these Layer 2 technologies arenot affected by the Stretched Subnet Mode of the present disclosurebecause the Stretched Subnet Mode occurs at Layer 3.

A “router on a stick” is a term commonly used in the networkingindustry, and can sometimes be referred to a “stub router”, “one-armedrouter”, etc. A LISP router within the context of the disclosureincludes a network router having LISP functionality enabled/implementedthereon. The LISP router may be an aggregation services router (ASR).For network elements in different subnets or within the same subnet tocommunicate (e.g., network elements at the first location, networkelements at the second location, network elements at the wide areanetwork 310), the LISP router (a Layer 3 device) is provided to routebetween the subnets when traffic needs to be routed between locations. ALISP router (configured) on a stick may have a single Ethernet NetworkInterface Card that is part of two or more subnets (thereby providing atrunk) enabling the two or more subnets to communicate. For instance,the LISP router on a stick joins any subnet(s) at the first locationwith subnet(s) at the target DC. When traffic needs to travel from theoriginal DC to the network elements at the target DC, the traffic mustbe routed by the LISP router configured on a stick.

The LISP router on a stick also means that the LISP router isnon-intrusive, and the LISP router is not the default gateway fornetwork elements at original DC. The LISP router is not on the data pathnor is the LISP router the default gateway for network elements at theoriginal DC prior to migration. Such “router on a stick” configurationrequires no change on the routing at the original DC, and the subnet(e.g. “10.1.1.0/24”) continues to be advertised to the wide area network310 by the first location (e.g., the original data center).

FIG. 4 is a simplified diagram showing a data path between a server onthe subnet where mobility is needed and a network element on the widearea network, according to some embodiments of the disclosure. Prior tomigration, the data path 402 between a second network element 404 (e.g.,a user communicating with a server 10.1.1.5) on the wide area network310 and the first network element 306 does not traverse the first LISProuter 302 a configured on a stick. Traditionally, LISP had always beenproposed to be deployed on the routers that are the default gateway.This previous model is disruptive for the original data center (DC). Instark contrast, the present disclosure requires the LISP router to beconfigured on a stick, which is far less intrusive to the original DC.This “router on a stick” configuration to place the LISP router in theoriginal DC without being in the data path (until migration requires it)solves a major objection for LISP introduction in a productionenvironment.

FIG. 5 is a simplified diagram showing detection of a server on thesubnet where mobility is needed; according to some embodiments of thedisclosure. By being connected to the same subnet where migration is tobe performed (or where mobility is needed), the first LISP router 302 acan detect the first network elements 306 and a third network element308 (hosts/servers identified by the “EIDs”) by listening to AddressResolution Protocol (ARP) messages that may be sent by the networkelements themselves (announcing their identity, e.g., “10.1.1.5” and“10.1.1.6”), for example during boot up time, or by initiating traffic(e.g., transmitting an Internet Control Message Protocol request) to thenetwork elements 306 and 308 in the subnets to be migrated. Listeningfor ARP messages allows a mapping to be made between locations of theLISP routers (or other suitable RLOCs) and the IP addresses of thenetwork elements at the same location of the LISP routers (or othersuitable EIDs). In this example original DC, the first LISP router 302 ais located at “2.2.2.2”, and the other LISP router 302 b for redundancyis located at “3.3.3.3”. In this example target DC, the second LISProuter 304 a is located at “4.4.4.4”, and the other LISP router 304 bfor redundancy is located at “5.5.5.5”.

In this illustration, the first LISP router 302 a detects the firstnetwork element 306 having a first IP address (e.g., “10.1.1.5”) at thefirst location prior to the migration, and stores an entry in themapping database mapping the first IP address to the location of thefirst LISP router (e.g., “10.1.1.5->2.2.2.2”, or if redundant LISProuters are used, “10.1.1.5->2.2.2.2/3.3.3.3”). The first LISP router302 a also detects the third network element 308 having a third IPaddress (e.g., 10.1.1.6) at the first location prior to the migration,and stores an entry in the mapping database mapping the third IP addressto the location of the first LISP router (e.g., “10.1.1.6->2.2.2.2”, orif redundant LISP routers are used, “10.1.1.6->2.2.2.2/3.3.3.3”). Theuse of a mapping database allows the LISP system to know the location ofeach network element (e.g., servers) and for LISP routers to updatetheir respective caches of the mapping database if applicable,advantageously allowing users to easily check where a network element islocated.

After the Network Element(s) Move

FIG. 6 is a simplified diagram showing updating of the mapping databaseand cache(s) of the mapping database for at least two LISP routers aftera server is migrated to the target data center. The first networkelement 306 (having the first IP address “10.1.1.5”) has been moved fromthe original DC (i.e., the first location) to the target DC (i.e., thesecond location). The second LISP router at the target DC (i.e., thesecond location) detects the first network element 306 having the firstIP address is now located at the second location. For instance, thesecond LISP router 304 a may listen to Address Resolution Protocol (ARP)messages that may be sent by the first network element 306 (announcingtheir identity, e.g., “10.1.1.5), for example during boot up time, or byinitiating traffic (e.g., transmitting an Internet Control MessageProtocol request) to the network elements 306. Note the importantfeature of keeping the same IP address (i.e., “10.1.1.5”) that the firstnetwork element 306 used when connected to the subnet “10.1.1.0/24” atthe original DC (the first location), even when the first networkelement 306 is at the target DC (the second location). Also, note thesubnet “10.1.1.0/24” did not change, and effectively the subnet isstretched between the original DC and the target DC. If the second LISProuter 304 a is configured with the same IP address of the defaultgateway address used by the first network element prior to themigration, the default gateway address does not have to change either,thereby minimizing changes to configuration for the first networkelement 306.

In this illustration, the second LISP router 304 a detects the firstnetwork element 306 having the first IP address (e.g., “10.1.1.5”) atthe second location. The second LISP router 304 a then updates themapping database (and a cache of the mapping database at the second LISProuter) to include an entry mapping the first IP address to the IPaddress of the second LISP router (e.g., “10.1.1.5->4.4.4.4”, or ifredundant LISP routers are used, “10.1.1.5->4.4.4.4/5.5.5.5”). In thisexample, the cache of mapping database located on the second LISP routermay have a mapping database, which includes entries“10.1.1.5->4.4.4.4/5.5.5.5” and “10.1.1.6->2.2.2.2/3.3.3.3”. The secondLISP router 304 a may transmit, via the mapping database (system), tothe first LISP router 302 a the entry to update (the cache of) themapping database of the first LISP router 302 a. This informs the firstLISP router that the first network element is now located at the targetDC with the second LISP router, and the traffic should be forwarded tothe second LISP router with the address “4.4.4.4”. The update allows thefirst LISP router to route, to the second LISP router, traffic targetedto the first network element through the first LISP router. Once themapping database and respective cache(s) are updated, the first LISProuter 302 a and the second LISP router 304 a are equipped with theproper information to locate the migrated network element 306 (and routetraffic targeted to the first network element appropriately), eventhough the first IP address (e.g., “10.1.1.5”) did not change when thefirst network element 306 changed its location from the original DC tothe target DC.

Proxy ARP and LISP Tunnel Between LISP Routers Across Locations

FIG. 7 is a simplified diagram showing responding to address resolutionprotocol request for the migrated server in order to route traffictargeted to the migrated server via a LISP router at the original datacenter, according to some embodiments of the disclosure. When trafficfrom the second network element 404 on the wide area network 310 istargeted to the first network element 306 having the first IP address“10.1.1.5”, the traffic is sent to the “10.1.1.0/24” subnet at the firstlocation (e.g., the original data center). The switch at first locationsends an ARP request, which is broadcasted, to locate IP address“10.1.1.5”, and the first LISP router 302 responds. Specifically, thefirst LISP router 302 a transmits to a first switch at the firstlocation to which the first LISP is connected on a stick, an ARP messageto inform the first switch to route the traffic targeted to the firstnetwork element via the first LISP router. In this manner, the firstLISP router 302 a provides a proxy ARP mechanism to attract traffictargeted for network elements at the target DC to itself.

FIG. 8 is a simplified diagram showing a LISP tunnel for transportingLISP-encapsulated packets between a LISP router at the original datacenter and a LISP router at the target data center in order to routetraffic from a network element on the wide area network to the migratedserver, according to some embodiments of the disclosure. Through theproxy ARP mechanism described in relation to FIG. 7, the first LISProuter 302 a may act as a LISP proxy ingress and egress tunnel router(PxTR) to transmit the traffic targeted to the first network element 306via a LISP tunnel 802 between the first LISP router 302 a and the secondLISP router 304 a. The second LISP router 304 a may be configured as aningress and egress tunnel router (xTR).

In some embodiments, the second LISP router 304 a (or some other LISPentity/server/router) is configured with a mapping server (MS or“Map-Server”) and a mapping resolver (MR or “Map-Resolver”) (i.e.,provided with their respective functions) to provide the mappingdatabase system for both, the first and the second LISP routers (and anyother LISP routers which queries or subscribes to the mapping database).The Map-Server and the Map-Resolver provides a “front end” for one ormore EID-to-RLOC mapping databases. The Map-Server, which learnsauthoritative EID-to-RLOC mappings from an Egress Tunnel Router (ETR) orProxy Tunnel Router (PxTR) and publishes them in a database. TheMap-Resolver, which accepts Map-Requests from an Ingress Tunnel Router(ITR) or Proxy ITR and “resolves” the EID-to-RLOC mapping using amapping database. Advantageously, Map-Server at the second LISP router304 a and MAP-resolver can be used by both, the first and second LISProuters such that the first LISP router 302 a can learn from the mappingdatabase (i.e., update their respective caches of the mapping database)that the first network element 306 is reachable via the LISP tunnel 802established between the first LISP router 302 a and the second LISProuter 304 a.

As seen in the FIGURE, a (horizontal) LISP tunnel 802 is established andprovided between two endpoints, i.e., the first LISP router 302 a andthe second LISP router 304 a. Upon attracting traffic targeted to thefirst network element 306, the first LISP router 302 a, acting as aproxy, transmits the traffic targeted to the first network element tothe second LISP router over a LISP tunnel 802 established between thefirst LISP router and the second LISP router. Likewise, the second LISProuter 304 a receives, from the first LISP router acting as a proxy viaa LISP tunnel 802 established between the first LISP router and thesecond LISP router, the traffic targeted to the first network element.Prior to transmitting the traffic over the LISP tunnel 802, the firstLISP router 302 a encapsulates the traffic targeted to the first networkelement 306 as LISP-encapsulated packets. This encapsulation removes, atthe first LISP router 302 a, any virtual local area network informationassociated with the first location from the traffic targeted to thefirst network element prior to transmitting the traffic over the LISPtunnel.

FIG. 9 is a simplified diagram showing a LISP tunnel for transportingLISP-encapsulated packets between a LISP router at the original datacenter and a LISP router at the target data center in order to routeintra-subnet traffic from a network element on the subnet at theoriginal data center to the migrated server, according to someembodiments of the disclosure. Traffic targeted to the first networkelement 306 originating from a third network element 308 connected tothe same subnet at the first location is also transmitted via the LISPtunnel 802 from the original DC to the target DC via the first LISProuter 302 a and the second LISP router 304 a.

Policy Routing and Symmetry: Returning Traffic for Stateful Devices

FIG. 10 is a simplified diagram showing a LISP router at the originaldata center for providing return traffic to a stateful device at theoriginal data center, according to some embodiments of the disclosure.In some embodiments, the original DC may include one or more statefuldevices, e.g., a Firewall or Load Balancer. These stateful devices maybe deployed as the default gateway on the original DC. Because the firstLISP router 302 a (and the redundant LISP router) is not configured as adefault gateway (as LISP routers normally in the traditionalimplementation would), the stateful devices can remain as the defaultgateway. This allows LISP to be used even on the case where there is aFirewall or Load Balancer as the default gateway on the original DC.Furthermore, by adapting the LISP router(s) at the original DC toprovide policy based routing, the return traffic from the target DC backto the original DC is diverted to the internal interface in order toensure symmetry in the path that the traffic travels (i.e., bringing thereturn traffic back to the stateful device on the right interface). Inother words, a policy is provided on the LISP routers at the original DCon traffic from the target DC to make sure to the “return traffic” isreturned to the correct interface on the stateful device at the originalDC (and not transported on the external interface of the LISP router).Specifically, the policy based routing at the LISP router at the firstlocation is applied based on the inner (EID address space) source IPheader so that traffic can be forced to be symmetric, returning to thestateful device (e.g., firewall or load balancer) on the same interfaceit originally traversed. Accordingly, when the first LISP routerreceives, from the second LISP router, return traffic from the firstnetwork element at the second location, the first LISP router transmitsthe return traffic from the first network element on an internalinterface to provide the return traffic to a stateful device at thefirst location.

Different LISP Deployment Models

FIGS. 11A-B illustrates possible deployment models of LISP routers.Traditionally, the LISP tunnels are implemented vertically, as seen inFIGS. 11A-B. In FIG. 11A, LISP is deployed on the customer sites as wellas on the customer Data Centers (i.e. LISP everywhere). In FIG. 11B, aPITR IS provided in the middle of the customer WAN and have non-LISPsites using it to reach the Data Centers (i.e. LISP partially deployedon customer WAN) The ingress tunnel routers (iTRs), and egress tunnelrouters (eTRs) shown are implemented as default gateways and tunnelsruns vertically between the user and the data centers.

FIG. 11C illustrates a deployment model corresponding to using LISP toenable migration of network elements without having to change the IPaddresses of the network element, according to some embodiments of thedisclosure. This new deployment model disclosed herein introduces athird option for LISP architecture, referred to as a “2-node LISP”model. On this new model LISP is only deployed on one node located deepinside the original DC, south of original DC aggregation layer, thisrouter is performing the PxTR function at the edge of the network andnot in the WAN, and the second node xTR is deployed on the new DC as thedefault gateway for the subnets where migration is needed. TheMapping-Server and Mapping-Resolver functions are also enabled on therouter on the new DC, making this deployment model self-contained onthose 2-nodes. As seen in FIG. 11C, the LISP tunnel runs horizontallyacross the data centers and stretches the subnet across both locations.For redundancy, this solution can be duplicated by duplicating thetunnel routers at the data centers.

Variations and Implementations

Within the context of the disclosure, a network used herein represents aseries of points or nodes of interconnected communication paths forreceiving and transmitting packets of information that propagate througha communication system. A network offers communicative interface betweensources and/or hosts, and may be any local area network (LAN), wirelesslocal area network (WLAN), metropolitan area network (MAN), Intranet,Extranet, Internet, WAN, virtual private network (VPN), or any otherappropriate architecture or system that facilitates communications in anetwork environment depending on the network topology. A network cancomprise any number of hardware or software elements coupled to (and incommunication with) each other through a communications medium.

In one particular instance, the architecture of the present disclosurecan be associated with a service provider deployment. In other examples,the architecture of the present disclosure would be equally applicableto other communication environments, such as an enterprise wide areanetwork (WAN) deployment, The architecture of the present disclosure mayinclude a configuration capable of transmission controlprotocol/internet protocol (TCP/IP) communications for the transmissionand/or reception of packets in a network.

As used herein in this Specification, the term ‘network element’ ismeant to encompass any of the aforementioned elements, as well asservers (physical or virtual), end user devices, routers, switches,cable boxes, gateways, bridges, loadbalancers, firewalls, inline servicenodes, proxies, processors, modules, or any other suitable device,component, element, proprietary appliance, or object operable toexchange, receive, and transmit information in a network environment.These network elements may include any suitable hardware, software,components, modules, interfaces, or objects that facilitate theoperations thereof. This may be inclusive of appropriate algorithms andcommunication protocols that allow for the effective exchange of data orinformation.

In one implementation, LISP routers described herein may includesoftware to achieve (or to foster) the functions discussed herein forenabling migration of network elements where the software is executed onone or more processors to carry out the functions. This could includethe implementation of instances of LISP routing modules, map-server,map-resolver and/or any other suitable element that would foster theactivities discussed herein. Additionally, each of these elements canhave an internal structure (e.g., a processor, a memory element, etc.)to facilitate some of the operations described herein. In otherembodiments, these functions for LISP routing may be executed externallyto these elements, or included in some other network element to achievethe intended functionality. Alternatively, LISP routers may includesoftware (or reciprocating software) that can coordinate with othernetwork elements in order to achieve the LISP routing functionsdescribed herein. In still other embodiments, one or several devices mayinclude any suitable algorithms, hardware, software, components,modules, interfaces, or objects that facilitate the operations thereof.

FIG. 12 shows an exemplary system diagram of an illustrative LISProuter, according to some embodiments of the disclosure. The LISP router1202 may include one or more processors 1204, one or more memoryelements 1206. In some embodiments, the LISP router includes a LISProuting module 1208 implemented thereon to perform the LISP routingfunctions described herein. A mapping database 1210 may also be providedto maintain mappings of EIDs to RLOCs for LISP routing purposes.

In certain example implementations, the LISP routing functions outlinedherein may be implemented by logic encoded in one or morenon-transitory, tangible media (e.g., embedded logic provided in anapplication specific integrated circuit [ASIC], digital signal processor[DSP] instructions, software [potentially inclusive of object code andsource code] to be executed by one or more processors 1204, or othersimilar machine, etc.). In some of these instances, one or more memoryelements 1206 can store data used for the operations described herein.This includes the memory element being able to store instructions (e.g.,software, code, etc.) that are executed to carry out the activitiesdescribed in this Specification. The memory element is furtherconfigured to store databases such as mapping databases to enable LISProuting functions disclosed herein. The processor can execute any typeof instructions associated with the data to achieve the operationsdetailed herein in this Specification. In one example, the processorcould transform an element or an article (e.g., data) from one state orthing to another state or thing. In another example, the activitiesoutlined herein may be implemented with fixed logic or programmablelogic (e.g., software/computer instructions executed by the processor)and the elements identified herein could be some type of a programmableprocessor, programmable digital logic (e.g., a field programmable gatearray [FPGA], an erasable programmable read only memory (EPROM), anelectrically erasable programmable ROM (EEPROM)) or an ASIC thatincludes digital logic, software, code, electronic instructions, or anysuitable combination thereof.

Any of these elements (e.g., the network elements, etc.) can includememory elements for storing information to be used in achieving the LISProuting, as outlined herein. Additionally, each of these devices mayinclude a processor that can execute software or an algorithm to performthe activities as discussed in this Specification. These devices mayfurther keep information in any suitable memory element [random accessmemory (RAM), ROM, EPROM, EEPROM, ASIC, etc.], software, hardware, or inany other suitable component, device, element, or object whereappropriate and based on particular needs. Any of the memory itemsdiscussed herein should be construed as being encompassed within thebroad term ‘memory element.’ Similarly, any of the potential processingelements, modules, and machines described in this Specification shouldbe construed as being encompassed within the broad term ‘processor.’Each of the network elements can also include suitable interfaces forreceiving, transmitting, and/or otherwise communicating data orinformation in a network environment.

Additionally, it should be noted that with the examples provided above,interaction may be described in terms of two, three, or four networkelements. However, this has been done for purposes of clarity andexample only. In certain cases, it may be easier to describe one or moreof the functionalities of a given set of flows by only referencing alimited number of network elements. It should be appreciated that thesystems described herein are readily scalable and, further, canaccommodate a large number of components, as well as morecomplicated/sophisticated arrangements and configurations. Accordingly,the examples provided should not limit the scope or inhibit the broadtechniques of using LISP routing for migration, as potentially appliedto a myriad of other architectures.

It is also important to note that the steps in the FIG. 2 illustrateonly some of the possible scenarios that may be executed by, or within,the LISP routers described herein. Some of these steps may be deleted orremoved where appropriate, or these steps may be modified or changedconsiderably without departing from the scope of the present disclosure.In addition, a number of these operations have been described as beingexecuted concurrently with, or in parallel to, one or more additionaloperations. However, the timing of these operations may be alteredconsiderably. The preceding operational flows have been offered forpurposes of example and discussion. Substantial flexibility is providedby the LISP routers in that any suitable arrangements, chronologies,configurations, and timing mechanisms may be provided without departingfrom the teachings of the present disclosure.

It should also be noted that many of the previous discussions may implya single client-server relationship. In reality, there is a multitude ofservers in the delivery tier in certain implementations of the presentdisclosure. Moreover, the present disclosure can readily be extended toapply to intervening servers further upstream in the architecture,though this is not necessarily correlated to the ‘m’ clients that arepassing through the ‘n’ servers. Any such permutations, scaling, andconfigurations are clearly within the broad scope of the presentdisclosure.

Numerous other changes, substitutions, variations, alterations, andmodifications may be ascertained to one skilled in the art and it isintended that the present disclosure encompass all such changes,substitutions, variations, alterations, and modifications as fallingwithin the scope of the appended claims. In order to assist the UnitedStates Patent and Trademark Office (USPTO) and, additionally, anyreaders of any patent issued on this application in interpreting theclaims appended hereto, Applicant wishes to note that the Applicant: (a)does not intend any of the appended claims to invoke paragraph six (6)of 35 U.S.C. section 112 as it exists on the date of the filing hereofunless the words “means for” or “step for” are specifically used in theparticular claims; and (b) does not intend, by any statement in thespecification, to limit this disclosure in any way that is not otherwisereflected in the appended claims.

What is claimed is:
 1. A computer-readable non-transitory mediumcomprising one or more instructions, that when executed on a processorconfigure the processor to perform one or more operations comprising:detecting, by a first Locator/Identifier Separation Protocol (LISP)router at an original location, a first network element having a firstInternet Protocol (IP) address at the original location prior tomigration; receiving, after the migration, at the first LISP router viaa mapping database from a second LISP router at a target location remotefrom the original location, an entry mapping the first IP address to theIP address of the second LISP router; wherein both the first LISP routerand the second LISP router are on the same subnet, and neither the firstLISP router and the second LISP router are on the data path for networkelements of the original location and the target location respectively;and updating, by the first LISP router, a cache of the mapping databaseat the first LISP router to configure the first LISP router to route, tothe second LISP router, traffic targeted to the first network elementthrough the first LISP router.
 2. The computer-readable non-transitorymedium of claim 1, wherein the network elements are migrated from theoriginal location to the target location without changing the InternetProtocol (IP) addresses, subnet mask, and default gateway of the networkelements.
 3. The computer-readable non-transitory medium of claim 1,wherein the operations further comprises: transmitting, from the firstLISP router to a first switch at the original location to which thefirst LISP router is connected, an address resolution protocol messageto inform the first switch to route the traffic targeted to the firstnetwork element via the first LISP router.
 4. The computer-readablenon-transitory medium of claim 1, further comprising: transmitting, fromthe first LISP router acting as a proxy to the second LISP router, thetraffic targeted to the first network element over a LISP tunnelestablished between the first LISP router and the second LISP router. 5.The computer-readable non-transitory medium of claim 1, wherein theoperations further comprises: encapsulating, by the first LISP router,the traffic targeted to the first network element as LISP-encapsulatedpackets prior to transmitting the traffic over the LISP tunnel.
 6. Thecomputer-readable non-transitory medium of claim 1, wherein theoperations further comprises: removing, at the first LISP router,virtual local area network information associated with the originallocation from the traffic targeted to the first network element prior totransmitting the traffic over the LISP tunnel.
 7. The computer-readablenon-transitory medium of claim 1, wherein the operations furthercomprises: receiving, at the first LISP router from the second LISProuter, return traffic from the first network element at the secondlocation; and transmitting, from the first LISP router, the returntraffic from the first network element on an internal interface toprovide the return traffic to a stateful device at the originallocation.
 8. The computer-readable non-transitory medium of claim 1,wherein the operations further comprises: in response to detecting bythe first LISP router the first network element at the originallocation, updating the cache of the mapping database with an entryassociating the first IP address with the IP address of the first LISProuter.
 9. The computer-readable non-transitory medium of claim 1,wherein the first LISP router is configured as a LISP proxy ingress andegress tunnel router to transmit the traffic targeted to the firstnetwork element via a LISP tunnel established between the first LISProuter and the second LISP router.
 10. A first Locator/IdentifierSeparation Protocol (LISP) router at an original location, the firstLISP router comprising: at least one memory element; at least oneprocessor coupled to the at least one memory element; and a LISP routingmodule that when executed by the at least one processor is configuredto: detect a first network element having a first Internet Protocol (IP)address at the original location prior to migration; receive, after themigration, via a mapping database from a second LISP router at a targetlocation remote from the original location, an entry mapping the firstIP address to the IP address of the second LISP router; wherein both thefirst LISP router and the second LISP router are on the same subnet, andneither the first LISP router and the second LISP router are on the datapath for network elements of the original location and the targetlocation respectively; and update a cache of the mapping database at thefirst LISP router to configure the first LISP router to route, to thesecond LISP router, traffic targeted to the first network elementthrough the first LISP router.
 11. The first LISP router of claim 10,wherein the LISP routing module is further configured to transmit, to afirst switch at the original location to which the first LISP isconnected, an address resolution protocol message to inform the firstswitch to route the traffic targeted to the first network element viathe first LISP router.
 12. The first LISP router of claim 10, whereinthe LISP routing module is further configured to: transmit, from thefirst LISP router acting as a proxy to the second LISP router, thetraffic targeted to the first network element over a LISP tunnelestablished between the first LISP router and the second LISP router.13. The first LISP router of claim 10, wherein the LISP routing moduleis further configured to: remove virtual local area network informationassociated with the original location from the traffic targeted to thefirst network element prior to transmitting the traffic over the LISPtunnel.
 14. The first LISP router of claim 10, wherein the LISP routingmodule is further configured to: receive, from the second LISP router,return traffic from the first network element at the target location;and transmit the return traffic from the first network element on aninternal interface to provide the return traffic to a stateful device atthe original location.
 15. A computer-readable non-transitory mediumcomprising one or more instructions, that when executed on a processorconfigure the processor to perform one or more operations comprising:detecting, at a second Locator/Identifier Separation Protocol (LISP)router at a target location, a first IP address of a first networkelement located at the target location, wherein the first networkelement was connected to a subnet at an original location prior to themigration using the same first IP address; updating, at the second LISProuter, a mapping database to include an entry mapping the first IPaddress to the IP address of the second LISP router; and transmitting,from the second LISP router via the mapping database to the first LISProuter located at the original location, the entry to update a cache ofthe mapping database at the first LISP router to configure the firstLISP router to route traffic targeted to the first network elementthrough the first LISP router to the second LISP router; wherein boththe first LISP router and the second LISP router are on the same subnet,and neither the first LISP router and the second LISP router are on thedata path for network elements of the original location and the targetlocation respectively.
 16. The computer-readable non-transitory mediumof claim 15, wherein the network elements are migrated from the originallocation to a target location remote from the original location withoutchanging the Internet Protocol (IP) addresses, subnet mask, and defaultgateway of the network elements.
 17. The computer-readablenon-transitory medium of claim 15, wherein the operations furthercomprises: receiving, at the second LISP router from the first LISProuter acting as a proxy via a LISP tunnel established between the firstLISP router and the second LISP router, the traffic targeted to thefirst network element.
 18. The computer-readable non-transitory mediumof claim 15, wherein the operations further comprises: configuring thesecond LISP router with the same IP address as a default gateway addressused by the first network element prior to the migration.
 19. A secondLocator/Identifier Separation Protocol (LISP) router at a targetlocation, the second LISP router comprising: at least one memoryelement; at least one processor coupled to the at least one memoryelement; and a LISP routing module that when executed by the at leastone processor is configured to: detect a first IP address of a firstnetwork element located at the target location, wherein the firstnetwork element was connected to a subnet at an original location priorto the migration using the same first IP address; update a mappingdatabase to include an entry mapping the first IP address to the IPaddress of the second LISP router; and transmit via the mapping databaseto the first LISP router located at the original location, the entry toupdate a cache of the mapping database at the first LISP router toconfigure the first LISP router to route traffic targeted to the firstnetwork element through the first LISP router to the second LISP router;wherein both the first LISP router and the second LISP router are on thesame subnet, and neither the first LISP router and the second LISProuter are on the data path for network elements of the originallocation and the target location respectively.
 20. The second LISProuter of claim 19, wherein: the traffic targeted to the first networkelement originates from a second network element connected to a widearea network, or the traffic targeted to the first network elementoriginates from a third network element connected to the same ordifferent subnet at the first location.